home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
-
-
-
-
- Update for INCON 3.1
-
-
- The following are notable differences from previous versions:
-
- * Input field handling has been moved into seperate modules
- for alpha, integer, float, and template fields. Each
- handler routine does its own character matching.
-
- * Floating-point fields are no longer treated as templates.
-
- * The Page flags are gone. One of the bits is used for the
- Mixed template type; the other for the Debug flag.
-
- * [Backspace] operation is fixed, so that it deletes the last
- character in the field instead of just pulling it along with
- the cursor.
-
- * Template, float, and hidden fields no longer use a special
- internal value to mark vacant field positions; they now use
- the Fill value passed in the message block. INCON.DOC
- includes a full explanation of the implications of that.
-
- * A "Stat Box" is available that shows all INCON parameters
- and flags after modification, if any, by field
- initialization. INCON.DOC has full details.
-
- * If the Debug flag is set, INCON automatically sets the
- Message flag. If the Message flag is not set, INCON does
- not display run-time error messages and pause until you
- press a key. Instead, it returns immediately with the error
- code. That may have led to confusion in previous versions,
- in which the demo program just bounced out of the test field
- when there was a run-time error. INDEMO.EXE, the
- demonstration program, sets the Debug flag each time it
- calls INCON with a new test field. Once you exit the field,
- Debug is cleared until you set up a new field.
-
- * The INDEMO menu has a much cleaner look; each field is
- accompanied by a line of explanatory text, displayed at the
- bottom of the sreen. INDEMO also has a pop-up help screen,
- tied to the [F1] key, that lists INCON's reserved keys. The
- help screen is provided mainly to demonstrate how to use
- INCON's extended-key trapping to provide special services to
- users, and how to use AddAttr() to prepare text to be moved
- into video memory. See INCON.DOC for details.
-
-
-
-
-
-
-
-
-
- Update for INCON 3.1 1
-
-
-
-
-
-
-
-
- Using the Make Files
-
-
- MAKE.BAT is supplied to run the make files; enter "make ?" or
- just "make" to see a help message. In addition to MAKE.BAT's named
- parameters, you can supply additional compiler switches and defines on
- the command line; MAKE.BAT concatenates them and stores them in an
- environment variable. The compiler command lines in the make files
- are set up to use that variable if it exists. Note, however, that you
- can't use ';' to gang X parameters or use '=' to define strings, since
- COMMAND.COM treats those characters as command-line delimiters.
-
- In the discussion of the make files below, an 'x' suffix appears
- on some file names. The suffix denotes the memory model, Small,
- Compact, Medium, or Large, under which the file was compiled.
-
- MAKE.BAT assumes that MAKE.EXE is in C:\TC and that the make file
- you want to process is in the current subdirectory. It also limits
- the choice of memory model you can compile under to the four listed
- above. If your home directory for MAKE.EXE is different, or if you
- want to be able to compile under the Huge memory model, make the
- required changes to MAKE.BAT. Memory models are set in the
- FOR...IN...DO statement.
-
-
- INDEMLIB.MAK
-
- Operates entirely within the current subdirectory. It creates
- INCONx.LIB from the INCON source files, and INDEMO.EXE using the
- library. Use this make file if you will be testing changes to INCON,
- and will be working mainly with one memory model.
-
- INDEMLIB.MAK creates object files with the same base name as the
- source files from which they were derived, no matter what memory model
- you compile under; be careful not to try to create a mixed-model
- library. You may create INCONx.LIB with or without debugging
- information through a MAKE.BAT option.
-
-
- INDEMO.MAK
-
- Creates INDEMOx.EXE in the current subdirectory from the INCON
- object files; it does not create a library. Object file names are the
- base name of the source file, plus the memory model suffix. You can
- keep a set of object and executable files for each memory model in the
- current subdirectory without conflict.
-
-
- INLIB.MAK
-
- Does an unconditional build of a "production" library, with no
- debugging information. It stores object files in \TC\USR and creates
- \TC\USR\INCONx.LIB from them. It then erases all of the object files.
- You can build INCONx libraries for small, compact, medium, and large
-
-
-
- Update for INCON 3.1 2
-
-
-
-
-
-
-
-
- memory models by invoking MAKE.BAT over-and-over with the relevant M
- parameter.
-
- If you don't have a \TC\USR subdirectory, or you want the
- libraries to go somewhere else, change the definition of O_DIR.
- INLIB.MAK adapts to changes in the output directory by creating a
- response file to build INCONx.LIB at run-time. It then moves the
- INCON header files into the output directory and creates a header file
- named INLIB.H. When you link INCONx.LIB to your programs, you need
- only
-
- #include "\outdir\inlib.h"
-
- to bring in the all of the required header files. Since MAKE.EXE
- doesn't allow redirection on the ECHO command, INLIB.MAK calls on
- INLIB.BAT to create the response file and move the header files.
-
- Before creating the new library, INLIB.MAK erases an existing
- library with the same name, but it still uses replace operations to
- create the new library. Therefore, you'll get "not found in library"
- warnings as TLIB attempts to extract each module from a non-existent
- library prior to adding it to the new library. If that bothers you,
- remove the "del" command that clobbers the old library, or change the
- response file to use add operations. The "del" command that purges
- the old .BAK copy of the library is also extraneous, since a .BAK copy
- is not created when the existing library is first deleted. If you
- prefer to keep the .BAK file around, or if you remove the line that
- deletes the existing library, remove that command also.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Update for INCON 3.1 3
-
-
-
-
-
-
-
-
- Files on the INCON 3.1 Distribution Disk
-
-
- ADDATTR ASM Assembly language routine that prepares text to be
- moved directly into video memory.
-
- STRINGZ ASM Suite of assembly language string-handling
- routines.
-
- INDEMRSP BAT Batch file called by both INDEMO.MAK and
- INDEMLIB.MAK to create the response files they
- need. If this file is missing, it may be
- recreated from comments at the beginning of either
- of the .MAK files.
-
- INLIB BAT Batch file called by INLIB.MAK to create the
- response file it needs and to move the header
- files required by "production" versions of
- INCONx.LIB into the output directory. If this
- file is missing, it may be recreated from comments
- at the beginning of the .MAK file.
-
- MAKE BAT Batch file for running the various .MAK files.
- Enter "make" or "make ?" on the command line to
- see a help message.
-
- INALPHA C Alpha field handler.
-
- INCON C Main loop, global initializations, run-time error
- handling, scrolling, and Stat Box.
-
- INDEMO C Demo source file.
-
- INFLOAT C Float field handler.
-
- INHELP C INDEMO help screen.
-
- ININTGR C Integer field handler.
-
- INTEMPL C Template field handler.
-
- INUTIL C Public utility routines.
-
- STRINGTS C Source file for STRINGTS.EXE.
-
- INCON DOC INCON documentation. If you want a hard copy of
- this file, it is formatted to print with standard
- settings (10 cpi, 66 lines/pg).
-
- INDEMO DOC INDEMO documentation.
-
- UPDATE DOC This file.
-
-
-
-
-
- Update for INCON 3.1 4
-
-
-
-
-
-
-
-
- INDEMOS EXE Small-model version of the INCON demonstration
- program.
-
- STRINGTS EXE Program for testing the routines in STRINGZ.ASM.
-
- ADDATTR H Header file for ADDATTR.ASM.
-
- INCON H Declarations for INCON.C.
-
- INDECL H Prototypes for public routines.
-
- INDEFS H Global definitions and declarations.
-
- INSTATS H Stat Box definitions and declarations.
-
- STRINGZ H Header file for STRINGZ.ASM.
-
- INDEMLIB MAK Creates INCONx.LIB and INDEMO.EXE in the current
- subdirectory.
-
- INDEMO MAK Creates INDEMOx.EXE in the current subdirectory.
-
- INLIB MAK Creates "production" libraries in the output
- directory.
-
- ADDATTR OBJ Object file created from ADDATTR.ASM, for those
- who don't have TASM. If that applies to you,
- don't destroy this or the next file, or you won't
- be able to rebuild them.
-
- STRINGZ OBJ Object file created from STRINGZ.ASM.
-
- INDEMO PRJ Project file for creating INDEMO.EXE from the
- Turbo C interactive environment. See INDEMO.TC.
-
- STRINGTS PRJ Project file for creating STRINGTS.EXE from the
- Turbo C interactive environment.
-
- INDEMO TC Turbo C configuration file for creating INDEMO.EXE
- from the Turbo C IDE. Building from the IDE is
- similar to using INDEMO.MAK, except that you can't
- add a suffix to output file names. When you do a
- Make, the new output files overwrite the old ones.
- If you plan to experiment with different memory
- models, its safest to do a Build All when you
- create INDEMO.EXE.
-
- If this file is missing or damaged, or you prefer
- to work with some other editor, set your tab size
- to 3 for all of the C source files. Otherwise,
- they will look pretty weird.
-
- STRINGTS TC Turbo C configuration file for creating
- STRINGTS.EXE from the Turbo C IDE.
-
-
-
- Update for INCON 3.1 5
-
-
-